I am having issues with both a Windows XP machine used as a print server, and a Windows 2003 R2 server where Vista SP1 machines are constantly leaving Open File connections listed as: \PIPE\spoolss. No matter what I do I cannot get them to stop. Windows XP machines will connect periodically to print, but only Windows Vista SP1 machines on our network will leave open sessions, wihch isn't a huge problem on the 2003 server, but on the XP printer server, it blocks other people from being able to print because the Vista machines are hogging all available connections. Does anybody have any ideas on how I can fix this? It looks like when XP first came out there was a similar problem with it leaving sessions open on Windows 2000 machines, and it required a patch from Microsoft: http://support.microsoft.com/kb/321364

Hi Jesse, i also have this problem, i have a Vista machine that keeps opening \PIPE\spoolss files constantly, the server is and SBS server with a couple of printers on it. None of the XP machines do this only this one Vista machine. I have been looking everywhere for a fix but have found nothing, you would think that a new OS like vista would not have this problem considering they fixed it with Windows 2000 with a patch. Anybody know how to fix this? Thanks again. Chris.

Hi Jesse, i also have this problem, i have a Vista machine that keeps opening \PIPE\spoolss files constantly, the server is and SBS server with a couple of printers on it. None of the XP machines do this only this one Vista machine. I have been looking everywhere for a fix but have found nothing, you would think that a new OS like vista would not have this problem considering they fixed it with Windows 2000 with a patch. Anybody know how to fix this? Thanks again. Chris.

Just wondering if you were ever able to find a resolution to this. I am having a similar issue but mine is between Small Business Server 2008 and an XP client. the XP client keeps getting connections to \pipe\spoolss which remain idle but are not closed, opened by the computer account of the server. this causes a shared folder on the client to eventually fail to accept new connections due to the 10 connection limit.

Just wondering if you were ever able to find a resolution to this. I am having a similar issue but mine is between Small Business Server 2008 and an XP client. the XP client keeps getting connections to \pipe\spoolss which remain idle but are not closed, opened by the computer account of the server. this causes a shared folder on the client to eventually fail to accept new connections due to the 10 connection limit.